Concerning the captcha problem...seems like the SeamResourceServlet, which delivers the captcha image doesn't get the same session data (the Captcha component) like the previous portlet render phase.(but StandardSession session-id is the same!)

The Seam Component Captcha is session bound and creates the question and expected answer in the init phase.

the request queryString:windowstate=normal&resourcestate=JBPNS_&type=portlet&resourceid=%2Fseam%2Fresource%2Fcaptcha&resourcecacheability=PAGE&phase=resource&windowid=%2Fsimple-portal%2Fdemo%2Fjsr-301.jsp%2F2&mode=view

I think you have another problem here. This souldn't be necessary! If a portlet renders a seam ressource link (h:graphicImage here), this link should work in the context of the same portlet session for a transparent usage.

my solution is really only a workaround...

so we have two problems remaining, no seam filters and seam ressource links live not in the same portlet session like the link rendering portlet.