I'm sorry you have had so much trouble with 3.3.3 and JSF 2. We have always meant the 3.3.3 to be a stepping stone for JSF 2 support, and as I said in my blogs ( 3.3.3.BETA1 and 3.3.3.CR1 ) and pointed to in the RichFaces 3.3.3 and JSF 2.0there are some limitations to the support that was possible in RichFaces 3.3.3.
One of these is the built in facelets support in JSF 2.0. We needed to make a trade off in between retro-fitting 3.3.X completely for JSF 2.0 ( a major undertaking ), or have limited JSF 2.0 support in 3.3.X and push forward with RichFaces 4.0 where we can really make great changes to get the most out of JSF 2.0. We realize that this is a problem for new development and part of the reason that we are working so hard to get RichFaces 4.0 out.
The goal of the JSF 2.0 support in RichFaces 3.3.3 is that you can run your existing RichFaces 3.3.X / JSF 1.2 applications in a JSF 2.0 / EE6 environment. New development taking advantage of all of JSF 2.0 features with RichFaces will need to wait for 4.0. The good news is that we are well on our way to our next 4.0 release, and will have several milestone releases to start your development with.