Ick, you're right. I was thinking solely about the change with their version of the "2>&1" vs "2>& 1" case.
Although making such an error in my example doesn't seem to invalidate my point. It takes an already odd syntax and makes it subtly different, instead of tightening it up.
FYI, "2>1" and "2 >1" already have very different results in Bourne shell. So I don't think it's an unforgivable sin.