Description of problem:
Backward compatibility problem with RichFaces a4j:push component.
(Backward compatibility verified by replacing RichFaces implementation binaries in latest released version from WFK 2.2 (2.2.0.CR2) (in this case 4.3.1.Final-redhat-1) in example from WFK 2.1 (2.1.0.Final))


Version-Release number of selected component (if applicable):
RichFaces binaries (richfaces-components-api.jar, richfaces-components-ui.jar, richfaces-core-api.jar and richfaces-core-impl.jar) version 4.2.3.Final from Metamer application obtained from WFK-2.1.0.Final maven repository by version 4.3.1.Final from WFK 2.2.0.CR2

How reproducible:
On following page: http://localhost:8080/metamer/faces/components/a4jPush/simple.xhtml

Steps to Reproduce:
1. build Metamer application from wfk21 branch (version 2.1.0.Final)
2. obtain richfaces-*.jar version 4.3.1.Final (available in WFK 2.2.0.CR1, 2.2.0.CR2 maven repository)
3. unzip metamer-jee6.war, and replace richfaces-*.jar files (version 4.2.3.Final) by version 4.3.1.Final
4. deploy metamer-jee6.war to jboss-eap-6.0
5. open http://localhost:8080/metamer/faces/components/a4jPush/simple.xhtml
6. in push updates area (introduced by "Last message:" label) expected default text "waiting for data from server..." replaced by something like: "Push Bot: Hello, still alive!" followed by timestamp from last push update e.g.: "[Apr 15, 2013 12:30:48 PM]"
7. Message remain "waiting for data from server..." instead of expected bahvior
  
Actual results:
No push updates receiving on a4j:push example page.

Expected results:
Receive/display message using form: "PushBot: still alive!" followed by timestamp from last push update.

Additional info:
No error in log discovered. Seems it just doesn't work with this configuration.
JBoss EAP start with standalone.xml configuration. (Deploy metamer app fails if start JBoss EAP with standalone-full.xml configuration)
Push component in default metamer application (without richfaces implementation binaries replaced) is working correctly.