Kernel's v3.16.0-4-amd64 files left behind after updating my Debian oldstable/Jessie's Kernel. Why?

[Ant]

Hello.

This morning PST, I did my daily apt-get update and upgrade earlier on
my Debian oldstable/Jessie and noticed:

$ ls -all /boot
total 45032
drwxr-xr-x 3 root root 4096 Jan 9 08:40 .
drwxr-xr-x 27 root root 4096 Jan 9 08:40 ..
-rw-r--r-- 1 root root 157756 Dec 14 13:27 config-3.16.0-4-amd64
-rw-r--r-- 1 root root 157786 Jan 9 03:42 config-3.16.0-5-amd64
drwxr-xr-x 5 root root 12288 Jan 9 08:41 grub
-rw-r--r-- 1 root root 16814543 Dec 16 18:38 initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 16814597 Jan 9 08:40 initrd.img-3.16.0-5-amd64
-rw-r--r-- 1 root root 98964 Mar 10 2015 memtest86.bin
-rw-r--r-- 1 root root 182704 Sep 10 2014 memtest86+.bin
-rw-r--r-- 1 root root 184840 Sep 10 2014 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 2684316 Dec 14 13:27 System.map-3.16.0-4-amd64
-rw-r--r-- 1 root root 2683305 Jan 9 03:42 System.map-3.16.0-5-amd64
-rw-r--r-- 1 root root 3137712 Dec 14 13:25 vmlinuz-3.16.0-4-amd64
-rw-r--r-- 1 root root 3139776 Jan 9 03:40 vmlinuz-3.16.0-5-amd64

$ cat /var/log/apt/history.log
Start-Date: 2018-01-05 09:30:28
Commandline: apt-get dist-upgrade
Upgrade: google-chrome-stable:amd64 (63.0.3239.108-1, 63.0.3239.132-1)
End-Date: 2018-01-05 09:30:38
Start-Date: 2018-01-09 08:39:50
Commandline: apt-get dist-upgrade
Install: linux-image-3.16.0-5-amd64:amd64 (3.16.51-3+deb8u1, automatic),
linux-headers-3.16.0-5-common:amd64 (3.16.51-3+deb8u1, automatic),
linux-headers-3.16.0-5-amd64:amd64 (3.16.51-3+deb8u1, automatic)
Upgrade: libpoppler-glib8:amd64 (0.26.5-2+deb8u1, 0.26.5-2+deb8u2),
libpoppler46:amd64 (0.26.5-2+deb8u1, 0.26.5-2+deb8u2),
libpoppler-cpp0:amd64 (0.26.5-2+deb8u1, 0.26.5-2+deb8u2),
libpoppler-qt4-4:amd64 (0.26.5-2+deb8u1, 0.26.5-2+deb8u2),
linux-image-amd64:amd64 (3.16+63, 3.16+63+deb8u1),
linux-compiler-gcc-4.8-x86:amd64 (3.16.51-3, 3.16.51-3+deb8u1),
linux-headers-amd64:amd64 (3.16+63, 3.16+63+deb8u1), poppler-utils:amd64
(0.26.5-2+deb8u1, 0.26.5-2+deb8u2), linux-libc-dev:amd64 (3.16.51-3,
3.16.51-3+deb8u1), gir1.2-poppler-0.18:amd64 (0.26.5-2+deb8u1,
0.26.5-2+deb8u2)
End-Date: 2018-01-09 08:41:02

Shouldn't Kernel's v3.16.0-4-amd64 files be automatically removed like
in the past with previous kernel upgrades? Is it a bug? I am tight on
free disk space in /boot in my very old desktop PC's 115 GB SSD. :(

Thank you in advance. :)
--
"This is the ant. Treat it with respect. For it may very well be the
next dominant lifeform of our planet." --Empire of the Ants movie
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ Personal Web Site http://antfarm.ma.cx
/ /\ /\ \
| |o o| | If crediting, then use Ant nickname and URL/link.
\ _ / Axe ANT from its address if e-mailing privately.
( )

[Pascal Hambourg]

Post by Ant
Shouldn't Kernel's v3.16.0-4-amd64 files be automatically removed like
in the past with previous kernel upgrades?

Not necessarily. -5 is a new package, not an upgrade of -4.
Try apt-get autoremove if -4 was installed automatically as part of a
dependance. Otherwise you have to remove it manually.