JMS Reply Queue handles leaking on IBM MQ.

Using 3.1.11 and JMS we are seeing handles for our Reply Queue are being left open. 

This is using a SpringBoot application and IBM MQ client jars.

The most likely suspect is in JMSConduit the field 

staticReplyDestination is set to null on a JMSException but the existing MQQueue is never closed.

I have tried simulating the problem in IntelliJ by forcing a JMSException during the SendExchange.

Should there be a "ResourceCloser.close(

staticReplyDestination);" immediately prior to setting 

staticReplyDestination to null?