Your workaround seems reasonable.

The underlying problem is that the XML::SAX::Expat::Incremental module doesn't implement the full SAX API. That being the case, it really would be best if POE::Filter::XML didn't force it to be the default SAX parser.

I've submitted a patch which modifies POE::Filter::XML to directly instantiate the parser class it needs rather than using the ParserFactory.