Memory leak caused by retained connection ids in RemotingConnectorServer superclass

We're running 7.1.1, with a patch applied for REMJMX-45 to limit the worst leaks coming from the JMX subsystem.

However, even with this patch applied we can only survive for a few days in a production-like scenario.

It seems that org.jboss.remotingjmx.RemotingConnectorServer never calls the connectionClosed()/connectionFailed() methods in its superclass.
As such, the connection ids that are stored in the field javax.management.remote.JMXConnectorServer#connectionIds are never released.

Given sufficient connections made to a running instance of 7.1.1 (for example, various monitoring tools), an out-of-memory end-state is inevitable.