With the current setup, using dependencies, and deploying: A) -Bean1 w/ ControllerMode.ASYNCHRONOUS and a dependency on Bean2 -Bean2 w/ControllerMode.AUTOMATIC Bean1 is installed in a thread until the dependency is needed, at which point the thread is returned to the pool. Once Bean2 is installed in the main thread, Bean1 goes through the remaining lifecycle in the main thread. B) -Bean1 w/ ControllerMode.AUTOMATIC and a dependency on Bean2 -Bean2 w/ControllerMode.ASYNCHRONOUS Bean1 is installed in the main thread until the dependency is needed. Then I deploy Bean2, which happens in a thread, once Bean2 is installed resolveContexts(boolean) is then called from the thread, finds Bean1, but that is not associated with the thread and currently halts installation. I need to rethink how I'm attacking this. Maybe I'm being a bit too course-grained with where I am running ASYNCHRONOUS in a different thread, I'll see if I can make it happen later. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238030#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...