Clockwork\Request\Log::log will grow its log indefinitely resulting in a memory leak

When handling a lot of events during a longer process, php will run out of memory because all log messages are kept in memory. This is an issue for us as we expect the process to be alive for potentially millions of events.

Our current solution uses a wrapper around clockwork's logger, accesses the public property $messages that's available on clockworks's class and only keep the last 100:

$log = $this->clockwork->log();
if ($log instanceof Log === false) {
	throw new \LogicException("Expected log to be of type Clockwork\Request\Log");
}
$log->log($level, $message, $data);
if (count($log->messages) > self::MAX_LOG_SIZE) {
	array_shift($log->messages);
}

This works, but maybe it would be worth to consider including this (optional) behaviour out of the box.

Start at Clockwork\Request\Log::log and inspect how messages are retained in the public messages property. Determine how an optional retention limit could fit the existing logging behavior, then verify that long-running processes no longer keep an unbounded log while the default behavior remains clear.