One of the problems with Jellyfin is that older Live TV data is not deleted from the database even if all the guide sources and the TV tuner are removed from the configuration. The only way to ensure that the old metadata is gone, is by first stopping jellyfin:

systemctl stop jellyfin

and then editing the database manually to remove all Live TV data:

echo "DELETE FROM TypedBaseItems WHERE TYPE LIKE 'MediaBrowser.Controller.LiveTv.%;'" | sqlite3 /var/lib/jellyfin/data/library.db

After that, jellyfin can be restarted again, and all the Live TV channels and metadata should be gone:

systemctl start jellyfin

Due to containerization, applications running within an enclosed space will not notice the overall resource consumption such that freeing memory and expunging it might never take place. For that reason, Jellyfin seems to accumulate a lot of RAM within a Docker container that would otherwise be normal for its operation. Reported consumption can reach up to 3GiB even though most of that can be freed. The problem seems to affect glibc-linked programs under Docker and the solution is to set an environment variable named MALLOC_TRIM_THRESHOLD_ (last underscore is not a typo) to its lowest default value which is bytes.