Yes, with a first reply of:
As for your question, I’d recommend that you take a look at our ‘Optimizing your experience’ article here, going over how to remove assets from your library and other methods of reducing bloat.
However, this is worthless to this issue as it will only add more data that is being kept around and unused. For example, in the article it shows you how to use the image properties to make a smaller file, but unknown to the user both files are kept. So if you have a 10MB image that you use Image Properties to optimize down to 2MB, a normal person would assume that the 2MB shown in the Final Download Size tool is correct. However, in reality you increased your file size usage by 2MB to 12MB instead of reducing it by 8MB to 2MB. Then there is the issue that the file size reported after Publishing comes from the Final Download Size tool, not the actual size of what is uploaded. Even worse is if you instead replace the 10MB image with a 5MB image, and then replace that with a 2MB image your upload size is now 17MB not 2MB.
I just tested and verified what I noted above. Anything ever added into the Media Library will always be uploaded, but does not show in the Approx. Size or Final Download Size. Even if you replace or delete it from the Media Library it will still be uploaded.
24 hours later after I told them I was going to have to manually fix this issue they responded with:
Sorry for the inconvenience regarding your project’s size.
We’ve been able to compress (crush) your project ZPP down to 63MB using a method which we hope to make available via ZapWorks in the future to help clean projects, which should ensure faster publishing times for you.
A quick look at the zpp they sent and they did what I outlined here. I seriously hope this comes as a standalone tool ASAP and not as a 7.x feature.