Well as a developer I have my issues with that. Because you will probably want to log to local disk. And thats where a developer has usually no access to. Makes support difficult. Btw, you can dynamically establish the name of the log file at run-time and add a timestamp for example. (Unfortunately this doesnt work with logging to SQL Server)
Yep, that can be a problem, but our support folks have the access they need (or we store the log files on a network share so I can see them as needed). And to manage the size of the log files I do exactly what you said, dynamically configure the log file name to include a timestamp, per run of the package. Trades one huge log file for a bunch of small(er) ones, but at least you can open and read the log file. 🙂 Bit of a hassle to set up the first time, but once you've done it you can reuse it wherever you need.