Missing JAXBContextFinder from Entry objects unmarshalled as part of an Atom Feed

We're using RE to provide the Atom API in our jboss overlord s-ramp
implementation. Something we've run into is a performance problem
iterating over certain Atom Feeds. In some circumstances each Entry in
the atom Feed can wrap an additional jaxb object. We get access to this
via Entry's getAnyOtherJAXBObject.

This all works great except that there is no JAXBContextFinder set on
the Entry, so a new JAXBContext is created for each Entry.

I think the root of this problem is here:

https://github.com/resteasy/Resteasy/blob/master/jaxrs/providers/resteasy-atom/src/main/java/org/jboss/resteasy/plugins/providers/atom/AtomFeedProvider.java#L65-L68

Perhaps the finder should be set on the Entry either in all cases or
maybe only when Entry:getAnyOtherElement() returns a non-null?