I am working around this issue for now by annotating the filter class with @RequestScoped. Will have to test whether that has any negative effect on the non-Weld deployment. Oh, and BTW, it seems that the injected Application is whichever one is hit first, which makes sense. If the filter is essentially a singleton, then it looks as it did when it was first instantiated. |