The new Spring-based JMS Conduit should support using a shared permanent reply queue for several instances. The problem with temporary replyTo queues is that it is difficult to semantically associate the temporary replyTo queues with their original "request" queues. Using a named replyTo queue with a selector based on the correlationId solves this problem. This may be considered a "regression" introduced during the upgrade from CXF 2.1.2 to 2.1.3.
See Nabble Thread http://www.nabble.com/forum/ViewPost.jtp?post=20447067&framed=y.