-b 0.0.0.0 causes InstanceNotFoundException during JBoss shutdown

To reproduce, start JBoss EAP 4.3.0.GA with -b 0.0.0.0. You'll
see the following errors:

2008-02-07 16:40:29,866 ERROR [org.jboss.remoting.transport.Connector] invalid Object Name
javax.management.InstanceNotFoundException: jboss.remoting:service=invoker,transport= socket,host=hoge,port=3873 is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
at org.jboss.mx.server.MBeanServerImpl.unregisterMBean(MBeanServerImpl.java:383)
at org.jboss.remoting.transport.Connector.stop(Connector.java:744)

There are 3 errors, for each JBoss Remoting invoker with port
4457, 3873, 4446.

This behavior is introduced by JBREM-687 which is replacing
original locator (host=0.0.0.0) with
externalLocator (host=external address, not 0.0.0.0).

The MBean registration is done with 0.0.0.0 and unregistration
will fail because the replaced locater has external address.

http://jira.jboss.org/jira/browse/JBREM-687