Is it remotely possible there's a bug in 2.0-final that causes this behavior? I'm tempted to revert to 2.0b13 and see if the problem corrects itself.

No. The problem is purely mechanical, and completely unrelated to software.

Remember that many people had the problem long before that software version, and many people (including myself) ran 2.0 final for quite a while before the problem came up.

The fact that it happened to you when you installed 2.0 final was a complete coincidence.