Should $(fg) resume a stopped job?

[Oğuz]

    $ sleep 25
    ^Z
    [1]+  Stopped                 sleep 25
    $
    $ echo $(fg; jobs %)
    bash: jobs: %: no such job
    sleep 25
    $
    $ jobs
    [1]+  Running                 sleep 25 &

What I gather from this is that bash fakes interactive job control in
command substitution context, because otherwise `fg' wouldn't return
immediately. But I don't see any point in that `fg' resumes the stopped job
when it's faked. Is this a bug or a deliberate choice?

Oğuz