Speaking about .JBossInjectionProvider, you can ask Jboss team what does it mean.
In general, the number of jar files and some config parameters should be different if you launch the application in the JavaEE 5 environment. Currently, the examples are built to work within J2EE container (such as Tomcat 5.x)
Task to have different war files for most popular environments is in our TODO list.
Like Sergey said, the problem is that you are running a war that already contains the JSF implementation. In JEE5, the JSF impl is provided by the container. This is also the cause of the InjectionProvider error. Since you probably don't need injection for this app, it is not a problem.
BTW, the level should not have been FATAL. It should have been translated to a Log4J ERROR message. This is fixed in JBoss 5.0.
Anyhow, if you want to use a WAR that bundles the JSF implementation, you can still do that on JBoss 4.2 and JBoss 5. You just need to include the context param shown at the bottom of this wiki page:
In case nyone gets any Jasper errors, this is what you could do to solve the problem (Stan's solution)
If you remove everything between the <f:verbatim> </f:verbatim> in demo.jsp then it will work.
I did three things:
1) got rid of the WAR_BUNDLES_JSF_IMPL in web.xml
2) removed jstl.jar, jsf-api.jar, and jsf-impl.jar from WEB-INF/lib
3) fixed demo.jsp as per above