Looks like this was a known bug in Spring 4.2.0, upgrading to 4.2.1 has provided the expected functionality
That's a well-known – and thankfully already fixed – bug in Spring 4.2. Upgrading to Spring 4.2.1 should fix that (or Spring Boot 1.3 M5).