PSD saves color profile in "untagged" file, Bridge shows as embedded...

There is definitely something going on....

In the attached screen capture I started with the file in the upper left. This is a file that was originally AdobeRGB but the profile was not embedded (my working space is sRGB so it appears a little glum - that was also part of the test). I saved this file as a jpg, examined the exif and meta and didn't see any reference to AdobeRGB, and therefore it accurately displays bad color.

Then I resaved the same image as a PSD file, this is the image in the upper right. Both of the files in the upper row (photoshop view) look the same and had appropriately bad color in PS.

Next up... take a look at the row below, these are the previews in Bridge. On the left is the JPG version, it looks like the images as they appear in PS, but the image on the bottom right doesn't (look at the red patch which is the most obvious) this is the same image that is above. It is the Jpg that was resaved as a Photoshop file.

So.... what is Bridge doing with Photoshop files where they look different than the exact same file saved as a JPG. And unlike the example in the first post, I couldn't find any reference to Adobe RGB in the exif/meta data of the newly created PSD file. btw - I did try resaving with PS maximum compatible just incase there was a temp preview saved within the file. And, cache in Bridge was purged.