So while things have been bad in the past--they're getting better. Having everyone try to use s3 as a CDN has really forced the industry to evolve.
And in the case of major CDN providers like Level 3, removing assets is dead simple. They provide an API for you to pass assets to expire immediately. Or barring that, having a person spend 5 seconds on the keyboard to log into the control panel and paste in the URL to kill.
It is possible - the author of the Ars article had his pictures erased after writing the article.
Few people, even technologists, can grasp what it means to have 800 million users. Anything involving individuals just logging in is a non-starter.
Even Google can provide that level of support.
They had $4 billion in cash before the IPO. They'll have $9 billion after it.
Facebook may have set near-infinite Expires/Cache-control headers on their static content, since it never gets overwritten. In that case, the CDN never goes back to the origin to check if the file is still there. The CDN they are using probably does have the ability to explicitly remove files (e.g., to respond to DMCA take-down notices), but probably doesn't have the ability to do this at Facebook picture deletion scale.
In other words, Facebook probably can't do much about it unless they get the CDN provider to make a big investment, build their own CDN, or switch to another provider that does support it (usually a costly decision).