• Update:

    We upgraded the production server to SP1, and the issue is gone. Lunch for anyone who can figure out why it was happening 🙂