I'm 90% sure we fixed something related to this in 4.1, but the specifics escape me. Have you tried it on ORM 4.2.x?