Source Control Submitting via the engine does not accurately check for current Asset status

Licensee has found that when using the submit to source control option in the editor, assets which are deleted to a submitted changelist via the engine are re-uploaded when a person immediately uploads another asset from their build of the engine.

1. Create a New Project with No Starter Content
2. Add a Material
3. Create 3 Material Instances from the New Material
4. Submit to Perforce Source Control
5. On a new computer sync to this New Project
6. On the original computer delete the 3 Material Instances
7. Submit to Source Countrol via the Editor
8. On the New Computer, import a new asset
9. Submit the new asset to Perforce via the Editor

RESULTS: Deleted Assets are reuploaded

EXPECTED: The Engine should respect the submitted CL and not try to reupload the deleted files (This is how submitting via Perforce behaves with the assets.)