Dropping/creating procedure causes transaction log to empty
SQL Server acts like simple mode until you've established the log chain. This means that it will be happy to discard log information from already-committed transactions.

Paul Randal goes into a little more detail about the mechanics behind this here, but basically, this behavior will stop once you start proper backups:


New script: is that database REALLY in the FULL recovery mode?