Not at all. I meant that if your server doesn't serve much traffic it'll spend much of its time inside serve-socket blocked on a new connection. It's only after serving a connection that it'll loop around to check quitsrv.
I just ran an experiment, and indeed the server stops after one more request:
$ ./run-news
initializing arc..
ready to serve port 8080
arc> (= quitsrv* t)
; now browse to localhost:8080; page served
quit server ; printed by *serve*
; hit reload on localhost:8080; no response