Found the root cause of this. Remoting will always reuse the same internal client to a given locator. On InvokerRegistry.createClientInvoker if a previous locar was used with the same properties, the first locator will be used. On remoting there is a testcase testing this under org.jboss.test.remoting.lease.socket.multiple. If you change both connections to use the same id you will have the behavior described on this bug. so, to fix this we could either be doing the proper reference counting before stopping the lease, or having each connection setting a different nameId. Having each client Connection having a property differntiating locator will force each connection to open a new socket (which is what we wanted anyways I believe). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971839#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...