So what do You advise me to do now? Should I wait for fix or try to find some way aroud this issue (if exists) or move my project to the war archive (set of war archives) which would be quite weird in my opinion.
Project mentioned by Dan Allen (this one: https://github.com/dhinojosa/seam3_in_your_ear) does not work too.
I suggest that you deploy the war archives separately for now, until the bug is fixed in the application server.
There is a workaround for the issue:
The workaround works fine for single-webapp ear. Problems may occur if multiple web applications are packaged within the ear.