yeh just came across the same thing upgrading from 3.1.0 to 3.1.1
apparently it's a bug fixed in 3.1.3
https://jira.springsource.org/browse/SPR-9630