Excessive error reporting when virtual model's sources are removed (UUIDs, for example)

This was suggested by Dan. (Blame him, not me

Create a project
Create a physical model with a couple of columns
Create a virtual model, transforming from the physical
Save everything
(at this point there should be no warnings or errors in Problems)
Delete the physical model (click all applicable OKs)

I now have 5 errors:
1 - Sql transformation in the model vFizz contains the unresolved reference file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi#mmuuid/2a434440-3dcd-1124-891d-8961aeed3f64

2 - Sql transformation in the model vFizz contains the unresolved reference file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi#mmuuid/315c0f80-3dcf-1124-891d-8961aeed3f64

3 - Unresolved reference "file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi"

4 - Group does not exist: mmuuid:6c984d80-3dc9-1124-891d-8961aeed3f64

5 - Unable to resolve the imported model Fizz.xmi

Errors 1, 2, and 4 reference UUIDs and are, therefore, pretty useless to a user. Errors 3 and 4 are more useful. Can we get rid of the excessively "geeky" UUID references in these messages?

It also generates an entry in the Message Log:
Error 2009-02-20 13:37:29.431 Unable to resolve reference to a resource with the URI file:/home/pnittel/mmx/553ga/des/workspace/deletoid/Fizz.xmi

IMHO, I don't think a validation error should be in the message log.