I think you guys are nitpicking the level of objectivity/subjectivity. With any bug, first there needs to be a definition of what the bug is. Along with the definition of the bug, the solution or intented gameplay needs to be defined.
If you are going to preclude gameplay changes, then that pretty much precludes all bug fixes.
So, the question then becomes, where is the line drawn? At what point is a specific fix too much of a change? The answer to this question is entirely subjective and will vary from person to person. Person A might say that a bug fix is too much of a change. Person B might say that to not do it is not fixing the bug... in a sense, not fixing the bug is itself a gameplay change (from what was intended).
Then we must ask "what was the designer's intent?" Or, "did the designer even have an intent, or was this situation unforseen?"
As I said, there is a level of subjective analysis here that can be nitpicked to death. There's really no systematic solution to resolve this. The answer might be different each time, depending on the circumstances of each bug.
If this specific change is "over the line" to YOU, that's fine. However, please realize that there will be people who think that not making the change is equally "over the line".
Ultimately, the programmer (Bhruic in this case) needs to make his best judgment, and that is that. Asking for multiple versions is going down a road we really don't want to go down. I mean, what happens the next time? Okay, now we have 4 permutations. Do we ask him to make 4 versions of the patch?
Wodan