The beans are pooled inside the ThreadlocalPool. This means that each remoting thread is given an instance when asked. Depending on how many remoting threads you have it can take a while for the whole ThreadlocalPool to fill up. You can switch to a more traditional pool: StrictMaxPool, but this does introduce congestion on the semaphore regulating the pool. A completely different approach would be to optimize cache usage of your entities. Commonly the PostConstruct is only used for setting up resource connections to slow XA resources. You shouldn't store any data there that is common accross multiple stateless beans or data that is really state. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051288#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...