Users of FlashBlock, ClickToFlash, and platforms that don't support Flash (such as the iPhone) already know what would happen, and they like it.
Otherwise, it'd be Javascript + <canvas>, which so far is pretty darned fast, but not too friendly to ad-servers. Not Flash-fast, but speedy, and quickly getting faster. If JS+canvas gets more popular, you can bet that JS will get WAY more attention in this area.
Youtube HTML5 - 15-20% CPU
Youtube Flash - 20-25% CPU
.flv in Totem - 2-3% CPU
Clearly, there is optimisation work needed here.
(And there's no move towards parallel execution of in-page dom-touching JavaScript yet - web workers can't do it. Concurrency is such an issue that you can't even pass a function into a web worker in case it has bound variables - it's separate-script-and-message-passing only.)
I make games in Flash and performance is frequently an issue I and others battle against. The point at which Flash performance begins degrading is stupidly early.
Bloated, gif-based animated ads and/or HTML5 <canvas><audio><video> animated ads would take their place. (With, in many instances, much worse performance).
Flash isn't the issue; CPU-pegging animation, and ads, are the issue. The Medium != the Message.