I got the same problem on a SQL Server 2008, a general database failure (the files got deleted and the database was put offline by sql server at the same time)occured yesterday in 1 of our non-critical databases.

It was quickly restored but the replication was unable to work again, after spending a few hours looking I found out a new publication had been created on the restored database and that this was conflicting with the publication from for the crash.

This was strange since our company policy in such cases says that the old publication has to be removed and recreated. We found out that we could recreate the publication under the old name but their were still problems. Deleting it kept it in the replication monitor, this morning I once again recreated the publication under the same name and deleted it and the publication was removed in replication monitor.