No the way they're currently implemented.
1. This would require the target service to be specified in the incoming message (ESB unaware message) - currently set on the gateway configuration.
2. It would also require the registry to return the same gateway EPR for all "service:name" combo's being serviced by a particular Gateway "instance" - basically, the gateway would need to be registered n times for each Service it's providing external access to (not really a problem of course).
I think #1 there is probably the stickiest. I suppose you could achieve it be requiring the client to present the EPR it used to access the gateway, along with the message to be wrapped and routd to the target service. The Gateway could then figure out which service the message needs to be routed to from the EPR. Just a suggestion