Do you have any specialized class loading configuration?
Could you share jboss-deployment-structure.xml, application.xml, and any manifest.mf files that contain classpath, extensions, or module imports?
Ok so the behavior change is caused by a bug in 8.0.0 that prevented sub deployment isolation from getting honored, which now works correctly in 8.1:
I also notice that your web app has an empty Class-Path, so these two combined lead to your war not being able to see classes in your ejb jar. So you can either add a Class-path reference in your war's META-INF/Manifest.MF to point to your ejb jar. Or you could remove that isolation flag (or set it to false).
Let me know if that works for you.
BTW If you go the Class-Path route it would look like this:
Thank you. I just needed the to set isolated to false. It works with and without the Class-Path set.