The org.jboss.mq.server.Receivers interface
needs to be implemented with "set" semantics.

The list implementations currently don't do this, so the receiver can end up in the datastructure twice.
Since there is only one remove at unsubscribe, this causes a problem.