Resurrecting an old thread. We recently upgraded from 5.0.18 to 5.1.0.x and have unsuspectingly got hammered by this feature (bug).
When making application breaking changes like this between versions, it would be nice if there was a warning or error message for it. The docs are also out of date on this point, viz jira issue TAPESTRY-2757. Szemere
