Fix two memory leaks in syslogd

[dab]

Summary

Bug 198385
reports a memory leak in processing of forward actions. This
modification adapts the patch submitted with that bug (by Sreeram) to
fix the leak. While testing the modification, another leak was also
found and fixed.

Submitted by: Sreeram

Test Plan

Run valgrind on syslogd with at least one forward entry
(i.e., an action of @some-host). Send SIGHUP several times so that the
configuration file is reloaded. Send SIGTERM to terminate
syslogd. Before the change, multiple blocks of memory are reported to
have been leaked. After the change, no leaks are shown:

==34004== LEAK SUMMARY:
==34004==    definitely lost: 0 bytes in 0 blocks
==34004==    indirectly lost: 0 bytes in 0 blocks
==34004==      possibly lost: 0 bytes in 0 blocks

[hrs]

Looks good to me. Thank you for taking care of it!