It seems possible to have serveral instances of the org.jboss.invocation.http.server.HttpInvoker. You can just several mbean elements, each using a different JMX name, to a jboss-service.xml file. In the <invoker-proxy-binding> element in a deployment descriptor, you refer to the JMX name, which differ between the instances.
But from code inspection, it seems each instance will bind its delegate to the same JNDI name, 'invokers//http'. What consequences can this have? I have not seen any code that looks up the invoker in JNDI, so I wonder what puprose the JNDI binding serves?
The JNDI bindings serve no useful purpose as they are not used by anything and they should be removed.