Fixed in 1.6 Beta 3. This turned out to be a bug in the compatibility library (0x00700000) which was being loaded after the extension in question.

The fix is to load the compatibility library at the beginning (before all extensions) instead of before the first extension that needs it (which could be after other extensions).