I was wondering why, when I tried to schedule jobs with a task that I'd previously used with no issues, beaker began simply dropping that task from the jobs.

It turns out that I had a malformed Releases: field, which is obviously my fault. BUT, it's very, very dangerous that beaker was simply leaving that test out of execution without an error message: to the casual observer, my "tests" were passing. In reality, they were not even being run.