It's my experience that COM objects are much easier to maintain than are ASP pages, and they are likewise easier to integrate into multiple applications: say a Web-based order entry app and a Windows-based customer service app. If what you have is always going to be a Web app then ASP is the way to go. But, if you ever think you might be asked to build a more traditional app, then a multi-tiered COM approach is the way to go.
I know of an online bank that eventually fired their Web developerbecause he insisted on putting all their site's functionality in ASP pages rather than COM objects. They came along after he'd been working for a while and wanted, quite reasonably in my opinion, to build an internal application for managing their customers' accounts, and to provide customers with phone-based access to them. They had to rip out a lot of the functionality that was embedded in ASP and rebuild it as a set of COM objects. Took quite a bit of time.
As far as what happens to COM in a .NET world, it's not going anywhere. Most of Windows is built around COM, as are a bunch of applications, and Microsoft knows this. This pre-existing investment is one reason why they went to such pains to include backward compatibility with COM in .NET.