Seems that Spring regards pooling in general as beyond the scope of the springframework.
Spring often recommends reusing the J2EE container's capabilities such as for pooling & XA support.
Also Spring has support for general pooling such as for POJOs or JDBC connections via commons-pool.
In Spring 1.3 I think Juergen's working on a JMS consumer pooling layer which is kinda a mini-JCA container but that doesn't do XA and only works with inbound JMS - which can do the consumer side of JMS pooling.
Though if you've got a J2EE container (or can use Jencks), I'd recommend using that for pooling of JMS and XA JDBC resources as thats what its designed for, can work with or without XA and works well with inbound and outbound JMS as well as other APIs like JDBC and reuses Resource Adapters for the underlying resources.
I would receommend the Spring boys work Strachan's blog into their documentation or FAQ. Documentation Injection!
LOL :). Since writing that blog entry I figured it was kinda handy stuff to know so have added it to the ActiveMQ wiki if folks wanna link to it...http://activemq.org/JmsTemplate+Gotchas