Using static queue as a reply queue in InOut pattern causes memory leak in Network of Brokers

When using shared reply queues in a network of brokers, the churn in consumer updates (to update selectors) results in a build up of orphaned ConsumerInfo objects eventually causing the brokers in the network to run out of heap space.

This is observed when a replyToCacheLevelName of CACHE_SESSION or CACHE_NONE is set. When CACHE_CONSUMER is used, an increase in consumers per reply destination is not observed; however, dispatch is blocked by consumers with selector expression JMSCorrelationID='CamelDummyJmsMessageSelector' (See also ENTESB-11033).

Even if consumers and producers all attach to only one node in the broker cluster, a buildup of network consumers is seen on the opposite nodes in the cluster until an OOM condition occurs (the consumer counts on the node with attached consumers remains relatively constant)