Has this been confirmed yet? This is the one issue that's stopping us from completing the upgrade. Some guesses as to why this may be happening:

• a list of converters that executes in unpredictable order.
• A cached version is returned for a value and bypasses the converter

I will try to do some more investigation on this when I can.