This is related to
In our hands, the code that clears the requestcontext hashmap in the ClientImpl is no longer being called.
After a large load of client requests, a memory dump showed > 90% retained memory in the requestcontext hashmap of the ClientImpl.
Not sure whats going on but there is code in the CXFOutboundProcessor that is supposed to clear that hashmap, and it doesn't appear to be called. At one timeit was, but it might have been a victim of the change from cxf as a transport to cxf as a module.
The workaround was to use the SAAJ transformers and a http post.