This issue has been present since 2.11.0, but only became visible with the addition of the 'use warnings' pragma in 2.17.0.