To allow multiple AS instances to be started on the same machine without binding each to a separate address, services that open sockets need to integrate with the AS's ServiceBindingManager bean. The remoting connector EJB3 opens is such a service.
I'll attach such a version of the config file that allows this. Probably the biggest issue with its use is getting EJB3's testsuite to work when it is present, by providing a mock ServiceBindingManager impl.
If you guys don't want to deal with this for 5.0.0.CR2, we can change the AS build to have it provide its own version of the file in preference to the one that comes in jboss-ebj3-core.jar.