Are you using HA Naming or some other remote naming config? There seems to be a remote naming discovery happening on each JNDI lookup. The remote bcast fails, and the object is eventually found locally. Lagtastic for sure, but it doesn't appear to be Seam's fault. Can you try installing your app on a clean domain? I'd expect the problem to go away unless you've configured your EAR to include remote JNDI contexts or something. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957155#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...