Bit of an old thread, but issue we have had looks to be a known SQL 2012 bug. I have found the blog:
http://www.travisgan.com/2013/05/sql-server-2012-simple-recovery-model.html
Seems this issue will be resolved in CU7.
Hope this helps others who encounter same issue.
Thanks,
Sam