Extremely bad performance in JMS transport when the MessageListenerContainer is used

When configuring the JMS transport for a fixed queue and using the async api the MessageListenerContainer is used.
Normally this should increase the performance compared to jmsTemplate. When doing performance tests I found that the performance is extremely bad though.
(Few messages per second). When I profiled where time is spent I found that the ListenerContainer is shut down all the time and restarted on next call.

I removed the shutdown calls when no async messages are outstanding as the listeners may be kept open without any problems. Now the performance is fine again ( about 1500 request/reply calls per second).