The aim is to not have the service aware of how it is being used. The service is returned to jBPM to subsequently invoke method(s), so there is no suitable point in the code to do the thread cleanup. Imagine that there is some code in jBPM that logically does: - Get bean from context (invokes the Tapestry/SpringContext in the context chain to get the service bean) - Invoke service method <-- here is where we need to do thread cleanup - Continue with execution Hope this makes sense. Alfie. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242243#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...