Now that I try some tests this seems to be an issue with ANY NamedQuery that contains an update query. But really, could something this major have been missed or is there some subtle weirdness in my environment? I am also using Spring 4.0.