Because it's a horrible UX paradigm to require. If 'Save As...' had never existed, it wouldn't be unreasonable, but it is (was) a reasonable behavior that every other system I'm aware of has maintained.
This passive versioning thing is quite nice in some aspects, but it's very unknown with most people I've seen. They see a file changed, they assume it's stuck like that now and the original is gone forever. Why would they expect otherwise? Their unsaved file gave no indication of being saved. Every application they open it in, and everyone they email it to, will only get the most-recent version. Even the file-system doesn't tell you when you have multiple versions of something.
I like the feature, to be clear. I just think it's horribly executed, and the education side has been even worse.
The problem is that they took something. Then they changed it, giving it multiple nearly-invisible modes it can be in, which changes from application to application (not all have a 'revert' option, even for versioned files). Then they didn't tell anyone.
"Always assume that every change you make is saved automatically" - You must have had a hard time dealing with computers until now :)
The real-world analogy makes sense, but it doesn't fit with how things have behaved. This is likely an improvement overall, but it's creating a period of upheaval and damage to people's property where better notification of the changes would make it a non-issue.
To modify and drag out the analogy to absurdity: say you previously made cropped photos by photocopying with a white rectangle mask revealing only the portions you wanted duplicated. Now, suddenly, you find that photocopying with the mask in place crops your original photo, without telling you. Nested a layer deep in the photocopier's menu is an option to undo the changes to your original.
I claim this is fine... if and only if the photocopier tells you of this before or immediately after, so you know to copy the whole thing first, and then cut, or use the 'revert' option. In a couple years that may be unnecessary, but not right now.
When I spent hours in a wet darkroom, I used a masking frame and the enlarger head height adjustment to crop a print, having previously marked up a work print. The negative was untouched.
The larger point I am making is that by referring to 'real' objects, we will return to a point where there is no system wide consistency any more. Case in point: editing audio tape or cine film did destroy the edited version, which is why we used prints/copy tapes.
Disclaimer: I don't use Mac OS. I do look to Apple for UI design however.
iOS doesn't show "EDITED" next to the filename in any window title bars either. I would think most people seeing "filename.txt -- edited" in a window title bar (such as in osx 10.8 TextEdit) would assume the file has not yet been saved.
This passive versioning thing is quite nice in some aspects, but it's very unknown with most people I've seen. They see a file changed, they assume it's stuck like that now and the original is gone forever. Why would they expect otherwise? Their unsaved file gave no indication of being saved. Every application they open it in, and everyone they email it to, will only get the most-recent version. Even the file-system doesn't tell you when you have multiple versions of something.