This would be expected. A large transaction log would cause database mirror problems. Regular backups and truncation should be performed to the Simplify database transaction log to maintain a small size.

Microsoft KB Article - How to stop the transaction log of a SQL Server database from growing unexpectedly - http://support.microsoft.com/kb/873235

The database backup should be performed daily, possibly more often depending on the rate that the transaction log grows.