custom autobeam settings trashed by time sig?

[Kieren MacMillan]

Hi all,

In Lilypond 2.13.x, I'm finding that my autobeam overrides are being overridden 
every time I change [i.e., alternate] time signatures -- for example,

\version "2.13.17"
\relative c' {
  \time 2/2
    \overrideBeamSettings #'Score #'(2 . 2) #'end #'((* . (1 1 1 1)))
    \set Score.beatLength = #(ly:make-moment 1 4)
    c8 c c c c c c c
  \time 3/2 c c c c c c c c c c c c 
  \time 2/2 c c c c c c c c
}

Am I the only one that thinks this is not desirable behaviour? Do I really have 
to create my own functions like

twotwo = {
  \time 2/2
  \overrideBeamSettings #'Score #'(2 . 2) #'end #'((* . (1 1 1 1)))
  \set Score.beatLength = #(ly:make-moment 1 4)
}

and use that -- instead of "\time 2/2" -- in order to encapsulate (and thus 
hold on to) my beam settings? Or is there something about the mechanism that 
I'm misunderstanding?

Thanks,
Kieren.