Well the question seems answered now, its a bug from 5.20 onwards.

(?>...) still works like expected (and its better readable IMHO)

Seems like someone thought there should be a (erroneous) warning and patched the code.

The perldoc mentioning redundancy might have paved the way for accepting this patch too easily.

I'm surprised there was no unit test that alarmed p5p.