Apparent memory leak in JMX collector, possibly restricted to "weird" JMX transports

A newly upgraded Horizon installation, whose only job is to do JMX data collection from many JBoss (and perhaps other enterprisey) application containers, is exhibiting leaky behavior. With -Xmx=12G and nightly restarts already in place for unrelated reasons, system-wide performance slows to a crawl daily and JMX memory utilization resource graphs exhibit the classic monotonic-increase curve associated with a memory leak.

Eclipse MAT leak suspects report PDF is attached.

Sensitive assets available for internal retrieval:

• Heap dump
• Pre-chewed Eclipse MAT indices

Customer can produce logs, thread dumps, and any other necessary supporting materials upon request.