jessie-updates gives early access to stable packages which will eventually be added to Jessie in a point release.
A stable release of Debian (such as Debian 8 or 8.1) contains a fixed set of packages and versions. Some of these need updating, within the constraints of Debian's stable release process; once they're approved, such updates go to a proposed-updates section of the archive, and when a point release is made, they all migrate to stable. For some packages, where more urgent updates are required, there's an intermediate stage: they are made available in stable-updates (jessie-updates) before the point release. Currently, clamav and tzdata are available in jessie-updates; it certainly makes sense not to have to wait for a point release to get those updates.
Security-critical updates go through a different process and queue, and end up initially in jessie/updates on security.debian.org (the third set of entries in your example). The intent there is to provide the safest fix for security issues as quickly as possible, ideally at the same time as the security issue is announced. These updates are usually merged into the next stable update.
The Debian wiki has more details.
security.debian.orgto my answer later. Regarding your quote, that's talking about packages going into Debian in general, viaunstable(see for example December where we already have dozens of changes);stabledoesn't get many updates, the laststableupdate covered three months of changes and updated 66 source packages (so ~5 per week). – Stephen Kitt Dec 02 '15 at 07:53