See attached sample app to reproduce. I have tested it with 3.3.0 open source (easier to build as it's maven-built) as well as 3.3.0.GA_P02.
The sample app basically has a page with 2 links.
    <h:form id="frm">
        <h:commandLink value="Add component to tree"
                       actionListener="#{requestBean.addComponent}"/>
        <br/>
        <h:commandLink value="Trigger lifecycle"
                       actionListener="#{requestBean.doNothing}"/>
        <br/>
        <h:panelGroup id="pgrp" binding="#{requestBean.group}">
        </h:panelGroup>
    </h:form>

One link will dynamically add an HtmlOutputText component to an HtmlPanelGroup. the other link just triggers a jsf lifecycle.

If you remove the icefaces jar from the war, with PartialStateSaving set to true (default anyways), then the HtmlPanelGroup state will continue to add another HtmlOutputText when you click on a link. With the icefaces jar, you only ever get the last HtmlOutputText component and if you trigger a new jsf lifecycle, it clears all state of the HtmlPanelGroup.
The only way to maintain state with the icefaces jar is to set PartialStateSaving to false in web.xml:-
   <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
        <param-value>false</param-value>
and this is inconsistent with how JSF is behaving.
Customer has suggested a fix. (see diff attached).