Thanks for the response. I went down that same path. I was hoping there was some slick way of registering and EJB 3 session bean as the task handler but ran into the same things you did. I have it working now like you did - created an EJB 2 project with a single EJB 2 session bean as the task handler and deployed it in the same EAR as my EJB 3 application. The EJB 2 task handler process method can call out to my EJB 3 session bean(s).