I'd guess that this has to do with the scoping of servlet filters within ears. If two wars are published within the same ear what happens? I suppose you have your answer. Don't know if this is a bug or a feature of JEE deployment. This could also be a scoping problem with the JSF context. With both wars sharing a reference to the same JSF context. You may be able to specify a classloader isolation property in your wars to avoid this. Dunno. This is all pure speculation at this point. Although you have to ask yourself how a SeamNavigationHandler is getting called in a war that has no idea about Seam. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038056#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...