There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
When using JMSContext JMSProducers are only closed when JMSContext is closed which never happens in a life time of an application since that would negates any benefits of having JCA pool.
This could be easily observed when examining memory dump. It is possible to see a large accumulation of JMSProducer objects in memory.