Thanks. I should probably clarify that when I don't use the job-dsl-plugin, the branches with slashes work just fine (the jobs are auto-created without issue by the GitHub Organization Folder plugin). The job names show up in Jenkins with the slash, but the underlying job on disk has the URL encoded form. From that I assumed that maybe I should be passing the name with slashes to the job-dsl plugin, but it looks like it would treat it as a filename:
https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java#L144
e.g., given "org/repo/branch-name", where "branch-name" is "release/1.0", the plugin would think the jobName is "1.0".
That said, after looking at this plugin a bit more, it appears that it's meant to be used to fully manage the jobs and that mixing it with the GitHub Organization Folder plugin (
https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin) doesn't make sense since that plugin is creating the jobs, not job-dsl. (I was trying to use the job-dsl-plugin to modify jobs created by the github org folder plugin since some of the plugins I use have job-dsl support, but not pipeline support and I can run job-dsl from a pipeline)