Just to note.
This seams to be a problem with jQuery versions embedded on PrimeFaces an RichFaces.
I think that jQuery.noConflict could solve this issue.
What do you think about this?
This is fixed on primefaces issue #5219 (https://code.google.com/p/primefaces/issues/detail?id=5219) on version 3.5.1.
If you are a primefaces elite or pro member, just download the version 3.5.9 of primefaces.
If you are a community member, wait for the 3.6 version or checkout the source from google code (http://code.google.com/p/primefaces) and build it with maven.